Method to store programs for operator interface and the management of automation machines and/or plants and corresponding software product, or project format for the execution of the method

ABSTRACT

Project format, suitable to define functions and/or characteristics of an operator interface device or of a PLC of an operating machine, more generally of an industrial device. The project format comprises a base layer and a plurality of additional layers disposed in order on the base layer from the oldest to the newest.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims benefit of and is a National Stage entry fromPCT Application No. PCT/IT2019/050111, filed on May 21, 2019; whichclaims priority to and benefit of Italian Application No.IT102018000005547, filed on May 21, 2018, both of which are entitled“Method to Store Programs for Operator Interface and the Management ofAutomation Machines and/or Plants and Corresponding Software Product, orProject Format, for the Execution of the Method”, both of which areherein incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention concerns a method to manage a project format tostore programs for the operator interface and to manage machines and/orplants for industrial automation.

The invention also concerns a software product to execute the storagemethod.

By the term software product, the present invention concerns the projectformat that manages the operator interface (Human Machine Interface—HMI)between user and production plant, and the implementation logic of themanagement of the format itself. The present invention also concerns thefunctioning of a control device of a machine and/or plant, that is, ofany machinery or system for industrial automation, such as for example aProgrammable Logic Controller (PLC).

The present invention is applied in all cases where it is necessary tomanage or stabilize the functioning of an industrial device which caninteract with an operating machine and/or industrial plant.

BACKGROUND OF THE INVENTION

It is known that industrial devices, used on machines and/or plants forautomation, comprise a management program (runtime), which operates onthe basis of a project that defines the functionalities of the machineand/or plant.

By industrial devices we intend all the hardware architectures suitableto execute specific software, normally used in the industrial sector.

In the present invention, for ease of description, we will refer mainlyto HMI operator interface devices, but what is described can be extendedto other industrial devices, for example SCADA (Supervisory Control AndData Acquisition) supervision devices, or to the devices that manage theoperating machines, including PLCs.

It is also known that, to develop a project, it is usually necessary, orcustomary, to use a development environment, or IDE (IntegratedDevelopment Environment).

The IDE is structurally dedicated to the design of the functionalitiesof the HMI operator interface.

With the IDE, in particular, it is possible to define the interactionscreens with the machine operator and configure the functionalities ofthe HMI, such as for example alarms, or the field variables to read orwrite.

The state of the art provides that the project created using the IDE issaved in one or more files, usually in proprietary format. The projectin this form is called source project, since it is possible to reopen itagain in the IDE for further modifications.

In embedded systems, where there are fewer hardware resources, it iscommon practice for the source project to be in a compiled format, thatis, in the form of one or more files optimized so that the runtimeprogram of the embedded system is able to read, interpret and executeinstructions more efficiently and quickly. The compiling of the sourceproject is instead less usual in SC AD A systems. In fact, the runtimeprogram of these systems is usually being executed on PCs that havebetter hardware resources than embedded systems.

The compiled project, therefore, has specific form and purpose to beexecuted by the runtime, but not to undergo further modifications.

Furthermore, in most cases the IDE and the runtime are being executed ontwo distinct hardware architectures.

The IDE normally resides on a generic PC where the developer developsthe HMI project, while the runtime program resides on the operatorinterface device.

The transfer of the project, from the IDE to the runtime, occurs in aknown manner, for example through a network in which the PC and theoperator interface device are connected, or with the use of a USB key,or by other transfer means.

To execute the HMI project on the operator interface device of anoperating machine and/or plant, the state of the art provides thefollowing workflow:

-   -   design the functionalities of the operator interface on the PC,        through the IDE (the design usually occurs in the technical        offices of the manufacturer of the operating machine);    -   save the project in source format on the PC and, afterwards,        possibly compile it to make it executable by the runtime;    -   transfer the project to the operator interface device for        execution (the device is normally installed on the operating        machine at the customer premises, and therefore in a building        far from the manufacturer's design offices).

During the life cycle of the machine and/or of a plant, the operatorinterface is normally modified to satisfy, on each occasion, determinaterequirements, for example requested by the plant user or by theinstallation technicians.

Broadly speaking, the development of the operator interface of themachine and/or plant can comprise the following operating steps:

-   -   Design step: the project can be developed ex-no vo, or it can        start from a previous project, for example by creating a        customized variant of a series project. Normally, the design is        entrusted to the research and development staff of the        manufacturer of the operating machine and/or plant, and the        project is normally created at the respective technical office;    -   Modification of the project during the use or during the        installation of the operator interface device: during the        installation step it can be necessary to make modifications to        the HMI, to enable interaction with the other parts of the        machine and/or plant possibly designed by third parties, and        therefore not compliant with the communication standards of the        manufacturer. This step can be performed at the manufacturer's        technical office or directly at the site where the machine        and/or plant is installed during the commissioning step;    -   Personalization of the operator interface: this step can be        requested for multiple reasons, for example due to incomplete or        incorrect translations, perfecting the ergonomics, different        operating needs, or for easier access to common operations. In        particular, these modifications are required after the        installation of the device and/or after the start of normal        operating conditions;    -   Modification of the project in the steps following the        installation: the modifications to the operator interface are        implemented by the support technicians during maintenance,        upgrades, adaptations to new regulatory constraints, and similar        or comparable processes.

These operating steps are unsuited to the workflow that involvescompiling and transferring the project to run the HMI on the operatorinterface device.

Another disadvantage of the known solutions derives from the fact that,in the case of specific adjustments to the operator interface, forexample during the installation step, it is necessary to revisit thework flow, modifying the entire original project, or a copy thereof.

Another disadvantage of known solutions is that every modification onthe project entails a modification thereof, causing the loss of theprevious version.

It is possible, at most, to make a copy of the project before eachvariation, in order to guarantee that it is possible to return to thesaved point if the new modification does not meet the requirements. Ifit is possible to execute the modifications to the project, as well asin the development environment, also directly on runtime, the sourceproject format should be the same as the compiled project format toavoid transformations between the source project and the compiled onethat are not very efficient.

As already mentioned previously, the runtime and the developmentenvironment are usually being executed on two distinct hardwarearchitectures and therefore the source project is normally not optimizedfor the hardware performances of the operator interface device.

US 2011/0239190 describes a method for the customization of softwareapplications, which makes it possible to modify and customize thesoftware application, by one or more users, in a different way, withoutstoring multiple modified copies of the application. In someembodiments, the base objects for the software application and theoverlaid objects are stored in a datastore, and a runtime embodimentdetermines the execution of the overlaid objects instead of the baseobjects.

EP 2.746.931 and US 2007/0240096 describe other solutions of methods todynamically modify software applications.

The known solutions, however, do not allow to modify the project duringexecution thereof by the runtime, nor to isolate the modifications basedon the operating steps performed.

There is therefore the need to provide a new project format, and acorresponding storage and modification method, which overcomes at leastone of the disadvantages of the state of the art.

A first purpose of the present invention is to create a project formatthat adapts to the operating steps of development of the operatorinterface. Another purpose of the present invention is to develop aproject format that allows to intervene only on the part affected by themodification, and not to involve the entire project.

Another purpose of the present invention is to isolate the modificationsmade during one of the operating steps mentioned above, so that they canbe distinguished from the modifications made during the other steps.

Another purpose of the present invention is to simplify the modificationto the project, in particular, without there being the obligation tomake copies of the project for each variation.

Another purpose of the present invention is to propose a project formatwhich allows to make both temporary modifications to the HMI and alsopersistent ones.

According to the purposes of the invention, the modifications can bevalid for a period, that is, the termination of the operator interfacedevice is connected to a specific event.

According to further purposes of the invention, the modifications can bepersistent and therefore valid even after the shutdown and subsequentrestart of the runtime.

Another purpose of the present invention is to optimize a project formatthat allows it to be modified both by the IDE and also directly onruntime while the project itself is being executed.

Another important purpose of the present invention is to allow themodification of the project, or parts thereof, during the executionthereof by the runtime, isolating the modifications made so that theycan be distinguished from the rest of the project.

Another purpose of the present invention is to propose an optimizedproject format, usable both by the development environment and also bythe runtime, adapted for the hardware performance of the operatorinterface device on which the runtime is being executed.

The Applicant has devised, tested and embodied the present invention toobtain these and other purposes as highlighted below.

SUMMARY OF THE INVENTION

The present invention is set forth and characterized in the independentclaims, while the dependent claims describe other characteristics of theinvention or variants to the main inventive idea.

According to the present invention, in accordance with said purposes, amethod to store programs for the operator interface and to managemachines and/or plants for automation, wherein the program defines thefunctionalities of an HMI or of a PLC, or other, initially provides thestructuring of said program, or project format.

Said structuring of the program provides several layers, wherein thelayers comprise at least a base layer, generally created by the researchand development department of the manufacturer, and a plurality ofadditional layers, functionally specialized, above the base layer.

Unlike the state of the art, which provides that the program, or projectformat, is developed in a compact and monolithic manner, that is,consisting of a single block, the present invention describes thecomplete and functioning state of the project, incrementallyimplementing, on the base layer, in a desired and defined order, aplurality of additional layers of modifications to the project, whichprogress from the oldest one to the newest one.

In this regard, the program, or project format, thus developed allows toassociate with each of the layers an operating step of developing theoperator interface. In this way, each project layer contains all themodifications relating to at least one operating step. For example, allthe modifications relating to the testing phase or to a regulatoryadaptation can be contained in one layer.

Furthermore, the different layers of the project, possibly alsodeveloped by different operators, may not be modifiable by the designersof the upper layers. This guarantees a correct chain of responsibilitythat is easily traceable and identifiable.

It should be noted that the present invention provides the possibilityof modifying the base layer, or the previous additional layers, with acertain degree of flexibility, in this case maintaining unchanged, orrequiring controlled modifications, to the overlying and/or underlyinglayers in relation to the dominance.

It should be noted that, according to the invention, the additionallayers are dynamically created during the execution of the project. Inparticular, with each execution of the project the additional layers caninclude further modifications that depend on the current execution ofthe project.

It is further noted, and it is a distinctive reason of the presentinvention, that the creation of additional layers does not materializein a simple concatenation according to a certain order of pre-existinglayers, but that the layers, with the sole exclusion of the base one,are dynamically generated at runtime during the execution of the projectitself, wherein each of the modified layers contains the modificationsthat the operator has made using the project itself.

The additional layers can be further modified at each subsequentexecution of the project, allowing continuous and consequentialmodifications of the layers.

According to one aspect of the invention, the project format, dividedinto layers, allows to develop different projects starting from the samebase (possibly with the addition of one or more previous layers incommon).

Furthermore, the invention allows to produce, at any time, amodification layer above the others and then delete it. For example, itis possible to make modifications resulting from the experimentation tothe operator interface to evaluate whether to implement certainfunctionalities in the HMI.

According to a further aspect of the invention, each layer associatedwith a determinate operating step, or functional modification of theproject, does not necessarily have to include the whole set of functionsof the operator interface device, but can refer only to a functionalsubset. In this case, the layers associated with an operating step ofdevelopment of the HMI are positioned parallel on the same layer in theproject format, to the extent that the association is related.

According to a variant, said layers located parallel can coexist, sideby side, if they do not modify the same functional subset.

According to one aspect of the invention, the method to update asoftware product proposed by the present invention allows to make bothtemporary and also persistent modifications.

Temporary modifications to the operator interface arise, and develop, ina context, also contingent, of program execution.

For example, temporary modifications can refer to movements of graphicobjects within the operator interface which it is later decided to notimplement definitively. Persistent modifications, which can be lasting,must remain valid even if the there is a restart of the runtime. By wayof anon-restrictive example, the persistent modifications refer to theconfiguration of the display pages, or to the correction of atranslation.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other characteristics of the present invention will becomeapparent from the following description of some embodiments, given as anon-restrictive example with reference to the attached drawings wherein:

FIG. 1 shows a software product, or project format, according to thestorage method of the state of the art;

FIG. 2 schematically shows an embodiment of a software product, orproject format, according to the storage method of the presentinvention;

FIG. 3 shows an embodiment of a software product, or project format,according to the storage method of the present invention, wherein somelevels are positioned parallel on the same layer.

To facilitate comprehension, the same reference numbers have been used,where possible, to identify identical common elements in the drawings.It is understood that elements and characteristics of one embodiment canconveniently be incorporated into other embodiments without furtherclarifications.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

The following detailed description is provided by way of example anddoes not exhaust possible harmless variants or Implementations of theinvention.

Embodiments of the present invention concern a project format 10,comprising a base layer 11 and a plurality of additional layers 12.

The base layer 11, in this specific non-restrictive case, includes themain functionalities of the operator interface and serves as a platformfor the plurality of additional layers 12 which will progressivelyoptimize the HMI for the specific application.

The plurality of additional layers 12 is disposed on the base incorrect, chronologically sequential order, from the oldest to thenewest. Each additional layer 12 represents a modification to theoperator interface and produces one or more variations of the projectwith respect to the previous layers.

By way of example, according to a possible solution, each additionallayer 12 is associated with an operating step of developing the operatorinterface.

It should be noted that the present invention does not refer only to theoperating steps described above, given by way of example.

According to the invention, the inventive idea can be extended to otherdevelopment cycles, since the additional layers 12 can be associatedwith any operating step of the development of the HMI.

A similar argument can be made if the present invention is used for PLCmodifications or updates.

Even if the additional layers 12 are designed and disposed sequentiallyover the base layer 11, the present invention provides the possibilityof modifying the base layer 11, or the previous additional layers 12,with a certain degree of flexibility, maintaining the additional layers12 above unchanged or requiring minimal modifications thereto.

According to a further possible solution, the additional layers 12already designed cannot be modified by other designers.

The project format 10 thus structured allows to develop differentprojects, for example HMI but not only, starting from the same base 11.

This approach guarantees the maximum re-use of the various design steps,at the same time ensuring a high flexibility in the development of theoperator interface.

According to a possible solution, the project format 10 allows toconstruct at any moment an additional modification layer 12 above theothers, and then delete it.

According to a further possible solution, each additional layer 12 ofthe project 10 does not involve the modification of the entire set offunctionalities of the operator interface, but refers only to afunctional subset present therein. The layers 12 thus defined, whichbelong to the same operating step of the development of the HMI, arepositioned parallel on the same layer of the software product 10.

According to a further possible solution, the present invention allowsto make both temporary modifications and also persistent modifications,in order to allow the project format 10 to adapt to the differentcircumstances defined by the specific application case. The projectformat 10 of the present invention allows to save the modifications withrespect to the previous situation of any element of the project, or afunctional subset thereof.

According to the present invention, the project format 10 allows todescribe a plurality of variations between the layers that the projectconsists of In particular, the variations can refer to modificationsimplemented with respect to the previous project layers and can becreated, eliminated or modified during the development of the operatorinterface. In this regard, a development or storage method can beassociated with the project format 10 suitable to interpret saidvariations and develop the complete project version. The developmentmethod according to the present invention provides to start from thebase 11 and to progressively dispose the additional layers 12 referringto said variations.

According to a possible embodiment, the storage method according to theinvention is suitable to manage layers that insist on independent partsof the project, but which are associated with the same operating step,and which are disposed parallel on the same layer of the project format10.

The storage method according to the invention is able to understand,through the plurality of variations, whether the modification associatedwith a determinate layer is significant or not. In fact, in the case ofrepeated variations it is necessary to simplify the modifications thatare overwritten or invalidated by the subsequent ones.

In particular, the method allows to determine whether the modificationsintroduced are not invalidated by the modifications present in anadditional upper layer, so that only the variations significant for theproject in its entirety are preserved.

Furthermore, the storage method also intervenes in the case in which thedesigners modify the base layer 11 or the lower additional layers 12,managing to resolve possible conflicts in the additional layers 12above.

It is clear that modifications and/or additions of parts may be made tothe software product, and to the corresponding storage method, asdescribed heretofore, without departing from the field and scope of thepresent invention.

It is also clear that, although the present invention has been describedwith reference to some specific examples, a person of skill in the artshall certainly be able to achieve many other equivalent forms, havingthe characteristics as set forth in the claims and hence all comingwithin the field of protection defined thereby.

In the following claims, the sole purpose of the references in bracketsis to facilitate reading: they must not be considered as restrictivefactors with regard to the field of protection claimed in the specificclaims.

1. A programmable device, comprising an operator interface for operatingan industrial machine, wherein the programmable device is configured to:retrieve a project program from a storage, wherein the project programcorresponds to a project format, wherein the project format comprises: abase layer configured to control a first set of functionalities of theoperator interface; and a plurality of additional layers, wherein theplurality of additional layers is disposed in a chronological order onthe base layer, and wherein each additional layer of the plurality ofadditional layers is configured to be created dynamically at runtimeduring execution of the project program; and execute the projectprogram.
 2. The programmable device of claim 1, wherein each additionallayer of the plurality of additional layers is associated with anoperating step for developing the operator interface.
 3. Theprogrammable device of claim 1, wherein each additional layer of theplurality of additional layers is associated with a functional subset ofthe first set of functionalities of the operator interface.
 4. Theprogrammable device of claim 1, wherein a first additional layer of theplurality of additional layers comprises a plurality of operating stepsfor developing the operator interface disposed in parallel.
 5. Theprogrammable device of claim 1, wherein the base layer cannot bemodified by another group of developers.
 6. The programmable device ofclaim 1, further configured to: complete execution of the projectprogram; and re-execute the project program, wherein the plurality ofadditional layers is configured to be dynamically modified at runtimeduring the re-execution of the project program.
 7. The programmabledevice of claim 1, wherein at least one additional layer of theplurality of additional layers comprises a temporary modification. 8.The programmable device of claim 1, wherein at least one additionallayer of the plurality of additional layers comprises a permanentmodification.
 9. A system for programming a control system for operatingan industrial machine, comprising: a processor; and a memorycommunicatively coupled to the processor, wherein the memory havingstored therein computer executable instructions that, when executed bythe processor, cause the processor to: retrieve a project program from astorage, wherein the project program corresponds to a project format,wherein the project format comprises: a base layer configured to controla first set of functionalities of an operator interface; and a pluralityof additional layers, wherein the plurality of additional layers isdisposed in a chronological order on the base layer, and wherein eachadditional layer of the plurality of additional layers is configured tobe created dynamically at runtime during execution of the projectprogram; and execute the project program.
 10. The system of claim 9,wherein each additional layer of the plurality of additional layers isassociated with an operating step for developing the operator interface.11. The system of claim 9, wherein each additional layer of theplurality of additional layers is associated with a functional subset ofthe first set of functionalities of the operator interface.
 12. Thesystem of claim 9, wherein a first additional layer of the plurality ofadditional layers comprises a plurality of operating steps fordeveloping the operator interface disposed in parallel.
 13. The systemof claim 9, wherein the base layer cannot be modified by another groupof developers.
 14. The system of claim 9, wherein the computerexecutable instructions, when executed by the processor, cause theprocessor to: complete execution of the project program; and re-executethe project program, wherein the plurality of additional layers isconfigured to be dynamically modified at runtime during the re-executionof the project program.
 15. The system of claim 9, wherein at least oneadditional layer of the plurality of additional layers comprises atemporary modification.
 16. The system of claim 9, wherein at least oneadditional layer of the plurality of additional layers comprises apermanent modification.
 17. A method, comprising: retrieving, via aprocessor, a project program from a storage, wherein the project programcorresponds to a project format, wherein the project format comprises: abase layer configured to control a first set of functionalities of anoperator interface; and a plurality of additional layers, wherein theplurality of additional layers is disposed in a chronological order onthe base layer, and wherein each additional layer of the plurality ofadditional layers is configured to be created dynamically at runtimeduring execution of the project program; and executing, via theprocessor, the project program.
 18. The method of claim 17, wherein eachadditional layer of the plurality of additional layers is associatedwith an operating step for developing the operator interface.
 19. Themethod of claim 17, comprising modifying at least one additional layerof the plurality of additional layers, wherein the modification istemporary.
 20. The method of claim 17, comprising modifying at least oneadditional layer of the plurality of additional layers, wherein themodification is permanent.